\documentclass{beamer}
\usetheme{Warsaw}
\usecolortheme{whale}
\usepackage{pgfpages}
\pgfpagesuselayout{resize to}[a4paper,border shrink=5mm,landscape]
\title{Wormburner}
\author{Sean McMillan and Andrew Brazas}
\institute{University of Notre Dame}
\date{05/03/11}
\begin{document}

\begin{frame}
    \titlepage
\end{frame}

\section*{Problem}
\subsection*{Vision}
\begin{frame}
    \frametitle{Models}
    \begin{itemize}
        \item Traditional Model
        \begin{itemize}
            \item Manual effort
            \item Lack of access to history
        \end{itemize}
        \item Wormburner Model
        \begin{itemize}
            \item Mobile platform for historical data analysis
            \item Remove the tedious interruptions from golf 
        \end{itemize}
    \end{itemize}
\end{frame}


\subsection*{Two Models}
\begin{frame}
    \frametitle{Two Aspects to Wormburner}
    \begin{itemize}
        \item Automated Scorekeeping.
        \begin{itemize}
            \item Removes interruptions on every hole.
            \item Only exception is on drops or mulligans.
        \end{itemize}
        \item Statistical Views
        \begin{itemize}
            \item Golfers can now track progress while on the course or waiting to tee off.
            \item Views of specific holes can offer new insights.
        \end{itemize}
    \end{itemize}
\end{frame}

\section*{High-Level Solutions}
\subsection*{Use Case Diagram}
\begin{frame}
    \frametitle{Use Case Diagram}
    \begin{center}
        \includegraphics[scale=.25]{figures/use_case.png}
    \end{center}
\end{frame}

\subsection*{System Diagram}
\begin{frame}
    \frametitle{System Diagram}
    \begin{center}
        \includegraphics[scale=.25]{figures/system_diagram.png}
    \end{center}
\end{frame}

\section*{Physical Model}
\subsection*{Object Diagram}
\begin{frame}
    \frametitle{Object Diagram}
    \begin{center}
        \includegraphics[scale=.27]{figures/objectmodel.png}
    \end{center}
\end{frame}

\section*{Mock-Ups}
\subsection*{Home Screen and ScoreCard}
\begin{frame}
    \frametitle{Home Screen}
    \begin{center}
        \includegraphics[scale=.25]{figures/main_and_scorecard.png}
    \end{center}
\end{frame}

\subsection*{Course Map}
\begin{frame}
    \frametitle{Course Map}
    \begin{center}
        \includegraphics[scale=.20]{figures/course_map.png}
    \end{center}
\end{frame}

\subsection*{Statistics Main and Select a Game}
\begin{frame}
    \frametitle{Statistics Main and Select a Game}
    \begin{center}
        \includegraphics[scale=.25]{figures/statistics_and_select.png}
    \end{center}
\end{frame}

\subsection*{Course Selection and Statistics}
\begin{frame}
    \frametitle{Course Selection and Statistics}
    \begin{center}
        \includegraphics[scale=.25]{figures/course_select_and_statistics.png}
    \end{center}
\end{frame}

\section*{Costs and Conclusions}
\subsection*{Costs}
\begin{frame}
    \frametitle{Costs}
    \begin{itemize}
        \item \$74 266 spread over 3 months for a 3-man team
        \begin{itemize}
            \item UI develop, client-side developer, server-side developer
            \item \$8 000 per person-month
        \end{itemize}
        \item Process Maturity(App Development) is very high.
        \item Smaller team allows greater cohesion and communication.
    \end{itemize}
\end{frame}

\subsection*{Conclusions}
\begin{frame}
    \frametitle{Insights Gained}
    \begin{itemize}
        \item A lot more goes into project/software planning than initially thought.
        \item Preparation can go a long way to make the rest of the planning process smooth.
        \begin{itemize}
            \item Well thought out scenarios fill in objects quickly.
        \end{itemize}
    \end{itemize}
\end{frame}

\section*{Questions}
\begin{frame}
    \begin{center}
        Questions
    \end{center}
\end{frame}

\end{document}
